Predictive System for Deploying Enterprise Applications

ABSTRACT

Predictive systems for deploying enterprise applications include memory structures that output predictions to a user. The predictive system may include an HTM structure that comprises a tree-shaped hierarchy of memory nodes, wherein each memory node has a learning and memory function, and is hierarchical in space and time that allows them to efficiently model the structure of the world. The memory nodes learn causes, predicts with probability values, and form beliefs based on the input data, where the learning algorithm stores likely sequence of patterns in the nodes. By combining memory of likely sequences with current input data, the nodes may predict the next event. The predictive system may employ an HHMM structure comprising states, wherein each state is itself an HHMM. The states of the HHMM generate sequences of observation symbols for making predictions.

CROSS-REFERENCE TO RELATED APPLICATION

This application is related to concurrently filed and commonly assignedpatent application Ser. No. ______, filed on Mar. 15, 2013 and entitled“Predictive System for Designing Enterprise Applications,” which isincorporated herein by reference in its entirety.

TECHNICAL FIELD

The disclosed embodiments relate generally to predictive systems fordesigning and deploying enterprise applications.

BACKGROUND

Conventional systems for improved designing or deploying of enterpriseapplications have historically focused on more effective processingengines or drawing and modeling frameworks. These systems include toolsfor designing and deploying enterprise applications, but these includedtools have not addressed a common problem faced by users—that users haveto repetitively perform similar tasks when designing or deployingenterprise applications. The users are thus not provided with anintelligent system that guides them through the design and deploymentprocess. These systems are not “intelligent” because their tools focuson operating only on predefined instructions, which prevents them fromrecognizing patterns of enterprise application design and deployment. Asubstantial amount of time is therefore wasted by users repeatingsimilar tasks when designing or deploying enterprise applications. Thisamount of time becomes especially great when the users are employees ofa large corporation where similar design and deployment configurationsand tasks are performed multiple times by multiple employees on aregular basis.

SUMMARY

An objective of the present disclosure is to reduce repetitiveperformance of similar tasks. This problem is solved by an artificialintelligent system that can predict a sequence of actions that a usermay perform to design or deploy an enterprise application. Thispredictive system may employ a Hierarchical Temporal Memory (HTM) toeliminate the repetitions of tasks that encumber users in designing ordeploying enterprise applications.

Hierarchical Temporal Memory (HTM) models receive great attention fromvarious industries for their ability to learn and predict based on inputdata. Unlike standard computers that execute specific programs forsolving particular problems, systems employing HTMs replicate thestructural and algorithmic properties of a human neocortex, enablingthem to “learn” to solve diverse problems based on the input data. Suchsystems are thus able to independently infer and continuouslyself-improve through stored data and new input data that are fed intotheir hierarchy. HTMs are consequently known for their potentials forapproaching human level performance for cognitive tasks. HTMs areemployed in different fields but have in the past been known for theirapplications in pattern recognition.

A predictive system for designing and deploying enterprise applicationsmay include a Hierarchical Temporal Memory (HTM) structure comprising atree-shaped hierarchy of memory nodes. Each memory node in the structurecan have a learning and memory function. The nodes are hierarchical inspace and time, allowing them to efficiently model real-worldstructures. The memory nodes can learn causes and temporal beliefs,predict with probability values, and form beliefs based on the inputdata. Through this learning algorithm, the system stores likelysequences of patterns in the nodes. By combining the stored memory oflikely sequences with current input data, the nodes may predict the nextevent.

The predictive system may employ a Hierarchical Hidden Markov Model(HHMM) to perform the predictions and make inferences. An HHMM is astatistic model comprising states where each state is perceived as aself-contained probabilistic model. Each state of the HHMM is, thusitself an HHMM, which implies that its states generate sequences ofobservation symbols.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure and itsadvantages, reference is now made to the following description taken inconjunction with the accompanying drawings, in which like referencenumbers indicate like features, and:

FIG. 1 is a schematic diagram illustrating a general HTM structure;

FIG. 2 is a schematic diagram illustrating an HTM structure employed forpattern recognition;

FIG. 3 is a system diagram illustrating an embodiment of a predictiveconfiguration employing a predictive system connected to user interfacesvia a network or a cloud system;

FIGS. 4( a)-4(b) are schematic diagrams illustrating embodiments of apredictive system for designing applications based on process topologypatterns;

FIG. 4( c) is a diagram illustrating an embodiment of a process designedby a user;

FIG. 4( d) is a diagram illustrating an embodiment of an HTM receiving aprocess as an input;

FIGS. 4( e)-4(f) are schematic diagrams illustrating embodiments of apredictive system for designing applications based on process patterns;

FIG. 4( g) is a diagram illustrating an embodiment of a processcomponent with axes;

FIG. 4( h) is a diagram illustrating an embodiment of an HTM receiving aprocess component as an input;

FIG. 4( i) is a schematic diagram illustrating an embodiment of apredictive system for designing applications based on processcomponents;

FIG. 4( j) is a diagram illustrating an embodiment of an HTM where anode is activated;

FIG. 5 is a schematic diagram illustrating an embodiment of an HTMstructure used for a predictive system for designing applications;

FIGS. 6( a)-6(b) are schematic diagrams illustrating embodiments of apredictive system for designing applications based on model topologies;

FIG. 6( c) is a schematic diagram illustrating an embodiment of apredictive system for designing applications based on composite models;

FIG. 6( d) is a schematic diagram illustrating an embodiment of apredictive system for designing applications based on composite modelcomponents;

FIG. 6( e) is a diagram illustrating an example composite designed by auser;

FIG. 6( f) is a diagram illustrating an embodiment of an HTM receiving aSCA 1.1 composite as an input;

FIG. 6( g) is a diagram illustrating an embodiment of a compositecomponent with axes;

FIG. 6( h) is a diagram illustrating an embodiment of an HTM receiving aSCA 1.1 composite component as an input;

FIG. 6( i) is a diagram of an embodiment of an HTM that predicts basedon deconstructed SCA 1.1 composite input data;

FIGS. 7( a)-7(b) are schematic diagrams illustrating an embodiment of anHTM structure used for a predictive system for deploying applications;

FIGS. 8( a)-8(b) are schematic diagrams illustrating exemplaryembodiments of a predictive system for outputting configuration optionsfor designing applications and deploying applications, respectively;

FIG. 9 illustrates a process topology, composite topology, and ahierarchical composite model; and

FIG. 10 is a diagram illustrating an example HTM structure forpredictive deploying for a bank software application.

DETAILED DESCRIPTION

Methods and systems are described below for predicting a process fordesigning or deploying enterprise applications. Previous systems havefailed to address a common problem faced by users having to repetitivelyperform similar tasks. The presently disclosed system is a predictivesystem that employs Hierarchical Temporal Memories (HTMs), HiddenHierarchical Markov Models (HHMMs), or other suitable predictive modelsto predict sequences of user actions for designing or deployingenterprise applications based on input data. The system makes constantpredictions on the design and deployment configurations as a userdesigns or deploys an enterprise application. This reduces the amount ofsimilar and redundant tasks that a user has to perform when designing ordeploying enterprise applications. Furthermore, the predictive systemfor deploying configurations allows a new user or employee deploying anenterprise application to spend less time learning the differentconfiguration options. HTMs have excellent ability to learn and predictand are therefore employed in embodiments of the present disclosure topredict a next sequence of steps when designing or deploying enterpriseapplications.

I. General HTM Structure

FIG. 1 is a schematic diagram illustrating an HTM structure 100. As usedherein, the HTM structure 100 includes a hierarchy of levels 110 and120, where the level 110 has two memory nodes and the level 120 has onememory node. Each memory node has temporal and spatial memory spaces forstoring and processing information. The temporal memory space of eachmemory node stores sequential combinations of inputs that are often fedinto the memory node as temporal groups. The spatial memory space ofeach memory node may also store combinations of the inputs that areoften fed into the memory node at the same time as causes. The memorynodes at the level 110 are at the lowest level of the hierarchy andreceive the inputs 105. The memory nodes at the level 110 identifytemporal groups and causes of their inputs 105 by comparing the inputs105 with the stored temporal groups and causes. Based on the comparisonof the inputs 105 with the stored temporal groups and causes, the memorynodes at the level 110 may generate a specified or flexible number ofpredictions 145 with probability values 140. The predictions withhighest probability values are passed on to the next level 120 asbeliefs 111, 112. The newly identified temporal groups and causes arealso stored in the temporal and spatial memory spaces of the memorynodes at the level 110.

The beliefs 111, 112 are fed into the memory node at the level 120 asinputs. The memory node at the level 120 may discover temporal groupsand causes of its inputs, and generate a specified or flexible number ofpredictions 135 with probability values 130 based on stored temporalgroups and causes. The memory node at the level 120 may output a belief121 based on the predictions 135. The HTM structure 100 shows two levelsof memory nodes in its hierarchy, but other HTM structures may have anynumber of levels.

In short, each memory node (e.g., memory nodes at levels 110, 120)receives inputs from lower levels, discovers temporal groups and causesof those inputs, and generates predictions 135, 145 with probabilityvalues 130, 140. The predictions 135, 145 with highest probabilityvalues are selected as beliefs (e.g., 111, 112). The generated beliefsare, in turn, passed onto a memory node at a next higher level asinputs.

This process continues until beliefs are generated for memory nodes at ahighest level, which may be presented to a user as a predictedconfiguration option. Thus, all memory nodes are performingsubstantially the same learning algorithm, which means that each memorynode in the HTM is performing the same function as the overall HTM. Thatis, each memory node looks at the spatio-temporal pattern of its inputdata and learns to discover temporal groups and causes of this inputdata. For their excellent ability to analyze input data and stored datato perform cognitive functions, HTMs have often been employed forpattern recognition purposes.

II. HTM for Pattern Recognition

FIG. 2 is a schematic diagram illustrating an exemplary HTM system 200for receiving images of different parts of an aircraft to recognizepatterns and infer a name of an aircraft manufacturer. The HTM system200 includes a hierarchy of levels having memory nodes 205, 206, 230.Each memory node may have temporal and spatial memory spaces. Inputs201-204 at the lowest level of the hierarchy are images of differentparts of an aircraft. The inputs 201 and 202 are images of a leftaircraft engine section and a right aircraft engine section,respectively. The inputs 203 and 204 are images of a left aircraft wingsection and a right aircraft wing section, respectively. The inputs 201and 202 are fed into an Aircraft Engine Memory Node 205, and the inputs203 and 204 are fed into an Aircraft Wing Memory Node 206.

The Aircraft Engine Memory Node 205 compares the inputs 201 and 202 withits stored data to discover causes of the inputs 201 and 202. Based onthe causes, in the present embodiment, the Aircraft Engine Memory Node205 predicts with 90% probability 210 that the inputs 201 and 202correspond to a Boeing aircraft engine and with 10% probability 211 thatthe inputs 201 and 202 correspond to an aircraft engine manufactured byanother company such as Air Bus, Lockheed, and NASA. The prediction thatthe inputs 201 and 202 correspond to a Boeing aircraft engine has ahighest probability value, and is therefore passed up to an AircraftMemory Node 230 as a belief 220 generated by the HTM system 200.

Similarly, the Aircraft Wing Memory Node 206 predicts with 90%probability 212 that the inputs 203 and 204 correspond to a Boeingaircraft wing and with 10% probability 213 that the inputs 203 and 204correspond to an aircraft wing manufactured by another company. Theprediction that the inputs 203 and 204 correspond to a Boeing aircraftwing has a highest probability, and is therefore passed up to theAircraft Memory Node 230 as a belief 221. While not illustrated in FIG.2, if the inputs 201 and 202 and the inputs 203 and 204 wererespectively fed into the Aircraft Engine Memory Node 205 and theAircraft Wing Memory Node 206 in a sequential and not concurrent manner,then the memory nodes 205 and 206 would also discover temporal groups ofthe inputs 201 and 202 and of the inputs 203 and 204.

The beliefs 220, 221 are fed into the Aircraft Memory Node 230 asinputs, and based on these inputs, the Aircraft Memory Node 230discovers causes of its inputs 220, 221 and predicts with probabilityvalues 240-243. The Aircraft Memory Node 230 generates a belief 250based on predictions with the highest probability values. The predictionthat the inputs 220, 221 correspond to a Boeing aircraft has the highestprobability, and is therefore generated as the belief 250 that theaircraft is a Boeing aircraft. The belief 250 may be output to a user.Once again, while not illustrated in FIG. 2, the Aircraft Memory Node230 has the ability to discover temporal groups of its inputs as well.This illustrates how an HTM structure may be employed to recognizepatterns. The foregoing discussion of FIGS. 1 and 2 are provided toillustrate the operation of exemplary pattern recognition systemsemploying HTMs to provide context for use of the types of models for thedescribed inventive embodiments.

III. Predictive System Employing HTMs

FIG. 3 is a high-level system diagram illustrating an embodiment of apredictive environment 310 for designing and deploying enterpriseapplications. The predictive environment 310 includes a predictivesystem 311 that communicates with servers 312, a processor 313, asecondary memory 314, and web servers 315. The predictive system 311 mayinclude an HTM 301, a processor 302, and a secondary memory space 303.The HTM 301 may include a hierarchy of levels having memory nodes,wherein each memory node may have temporal and spatial memory spaces (asillustrated in FIG. 1 and FIG. 2). The memory 303 may store computerinstructions for carrying out a prediction functionality and theprocessor 302 may execute the computer instructions stored in the memory303. The HTM 301 provides prediction abilities for end-users that areaccessing the predictive system 311. The predictive system 311 isoperable to predict a next operation(s) or step(s) for designing anapplication or business process. Furthermore, the predictive system 311is operable to predict configuration options and details for deployingan application. This is useful because it provides a user who is notacquainted with the application the ability to select differentdeployment configuration options.

The predictive system 311 may be operated securely and remotely from endusers' user interfaces. Input data may be fed to the predictive system311 by the users that are operating on their user interfaces. Thepredictive system 311 may be accessible to users through differentmeans. In an embodiment, the predictive system 311 may be accessed by agroup of user interfaces 330 via a network 320 or by a group of userinterfaces 350 via a cloud system 340. While not shown in FIG. 3, thepredictive system 311 may more specifically be accessed by a group ofuser interfaces via the Internet, the World Wide Web (WWW), or othercommunication networks. The group of user interfaces 330 may includeuser interfaces #1(a), #2(a), . . . #n(a), and the group of userinterfaces 350 may include user interfaces #1(b), #2(b), . . . #n(b).Each user interface 360 may be an end user's local machine, which mayinclude a web interface 361, an application processor 362, an enterpriseprocessor 363, a main processor 364, a memory 365, a database 366,and/or other suitable components. The processor 364 may be a regular CPUof a computer. The user interfaces may essentially be any computingdevice, instance, or machine. And the memory 365 may be anyreadable-storage device such as CD-ROMs, read-only memories (ROMs),random access memories (RAMs), or floppy disks. While not illustrated inFIG. 3, the user interfaces may also include a voice recognition systemor a display.

The users may access the HTM 301 of the predictive system 311 via theprocessor 364 that uses the web interface 361 and the applicationprocessor 362, which are connected to either the network 320 or thecloud system 340. By accessing the data stored inside the HTM 301, theusers may access the predictive system 311 to predict the next sequenceof actions for designing or deploying enterprise applications. The userstransmit input data to the predictive system 311 by operating on a userinterface via the network 320 or the cloud system 340. In an embodiment,the predictive system 311 may be used for managing an application. Here,the input data may comprise one or more of a profile of a user, adepartment, a company, and an enterprise application. In anotherembodiment, the input data may be associated with a task and a link usedfor creating a business process. Once the predictive system 311 receivesthe input data and completes the predictions via its HTM 301, ittransmits the results back to the user interfaces via the network 320 orthe cloud system 340.

In other embodiments, an HHMM structure or other suitable predictivemodels may be employed to provide similar prediction abilities. Thepredictive system 311 may be employed for designing, managing,monitoring, or deploying an application. The predictive system 311 maybe coupled to different user applications for predicting the designingor deploying of enterprise applications. One possible user applicationmay be an application design studio where a user designs an applicationby selecting a task and the predictive system 311 predicts a next taskor tasks as options for the user. The application design studio may beEclipse or other software development environments, or a web studiobased on HTML 5, Scalable Vector Graphics (SVG), or other graphicslanguages. Furthermore, there may be similar embodiments employing thepredictive system 311 to predict a sequence of actions for modeling,managing, or monitoring an application. Management and monitoringsystems may be Administrators in Enterprise world. These are simplypossible embodiments and the application design studio is not limited tothese embodiments.

IV. Predictive Application Design

An embodiment of the predictive system shown in FIG. 3 may be employedmore specifically for predictive application design. In an embodiment,the predictive system 311 employing HTMs 301 is used for predictingapplication designs based on WS-BPEL 2.0. In another embodiment, thepredictive system 311 is used for predicting application designs basedon Service Component Architecture (SCA) 1.1. The predictive system iscapable of predicting the design involving WS-BPEL 2.0 and/or SCA, butother embodiments may involve other executable languages andarchitectures.

In an embodiment, a multiple level of hierarchy may be defined for anenterprise application. A top level may consist of the enterpriseapplication model and a bottom level may consist of model components.Each of the model components would be a part of the application model.Table 1 shows model components in a case of BPEL process model. Theapplication model is thus a collection of model components.

TABLE 1 Model Component Model Creation Actions Receive Task CreateReceive Task -> name -> assign partner link Invoke Task Create InvokeTask -> name -> assign partner link Reply Task Create Reply Task -> name-> assign partner link

For example, there may be three application models: (1) creating aprocess that receives a message and replies back; (2) a process thatreceives a message, invokes a service, and then replies; and (3) aprocess that receives a message, invokes a particular service based onthe message content, and then replies. The person designing a processthat receives a message and replies back will first have to create theprocess, name it, then create a receive task linked to the reply task.

The predictive system 311 is operable to predict a next task of anapplication model based on previously designed models and/or otherrelevant historical data. This embodiment employs an HTM 301, but otherembodiments may employ an HHMM structure or other suitable models.

The user interface 301 may more specifically be an application designstudio as shown in FIGS. 4( a)-4(b), FIG. 4( e), FIG. 4( f), and FIGS.6(a)-6(d). In an embodiment, a user may select a task, which gets fedinto the predictive system 311 as input data. Data of the task is fedinto the predictive system 311's HTM 301, thereby accessing andactivating a node that has the most similar pattern. The predictivesystem 311 will be able to predict a next design component, wherein thenext design component may be a next task(s) and/or next link(s) in anembodiment. In other embodiments, the predictive system 311 may make twoor more predictions. The predictive system 311 makes predictions basedon the input data and prior data that its memory nodes have received.The HTM 301 is thereby continuously inferring and learning throughexperience and new input data. These predictions may be output to theuser as options for the next action(s) to take for designing anapplication model.

Each memory node of the HTM 301 in the predictive system 311 may havespatial and temporal memory spaces that store combinations of inputs ascauses and sequential combinations of inputs as temporal groups,respectively. Thus, when input data, in an embodiment, a particulartask, is fed into a memory node, the memory node compares the input datawith its stored causes and temporal groups, and the HTM 301 outputs abelief on what the next link or task should be. The belief will then befed into a next higher level of the hierarchy of the HTM 301 as inputdata. The memory nodes at the next higher level of the hierarchy willcompare the input data with their stored causes and temporal groups, andthe HTM 301 outputs beliefs on what the next link or task should be. Thebelief at the highest level of the hierarchy of the HTM 301 will betransmitted to the user interface 360, which will then be presented tothe user as an option for the next sequence of action of the design. TheHTM 301 now has inferred causes and temporal groups from the input datasaved in its memory nodes. Thus, the HTM 301 is continuously learning.

In an embodiment, a user may load the HTM 301 with initial causes andtemporal groups so that it can begin inferring when new input data isfed into its nodes. The predictive system 311 performs these functionsby having a memory 303 that stores computer instructions for carryingout the described methods and a processor 302 that actually executes thecomputer instructions. The predictive system 311 may be accessed by anend user using the application design studio via a cloud system or alocal network. This allows accessibility for users located anywherearound the globe that has internet connection.

More specifically, the predictive system may predict design steps oroperations of an enterprise application by storing and receivingdifferent types of input data. The inferencing may be done using threedifferent methods. It may be based on deconstructed process patternsbased on topologies, process patterns, or process component patterns.

A. Based on Process Topology Patterns

FIG. 4( a)-4(b) illustrate a predictive system 411 that stores andaccepts input data from an application design studio 404. In anembodiment, the predictive system 411 may predict based on matching thetopology of the application being constructed with its stored data untilthe design of the application for a set number of model creation stepsis complete. The application model mapped on to the HTM has levels sameas the hierarchy of the model that defines the application. Thus, theapplication prediction is based on creating the HTM for each of themodel topologies that have been previously designed. In this embodiment,the form of data that the HTM 401 stores and receives is processtopology patterns based on WPEL 2.0. The HTM 401 receives deconstructedprocess topology patterns for a task 405 as input. The HTM 401 thendetermines and activates the nodes that have the most similar data asthe input data. In this embodiment, the accessed and activated nodes arerepresented with bold lines (e.g. node 440) while non-activated nodes(e.g. nodes 430, 450) are represented with dotted lines. The predictivesystem 411 then predicts a next link 406 and a next task 407, which arepresented to the user as an option for the next action to take, as shownin FIG. 4( a). Other embodiments may provide the next link 406, the nexttask 407, a next link 408, and a next task 408 as different options forthe user, as shown in FIG. 4( b).

Thus, in this embodiment, the predictive system 411 infers and predictsbased on how closely a deconstructed process pattern stored in its HTMmatches a WS-BPEL process being designed, or vice versa. In the presentembodiment, the deconstructed process pattern is based on a topology.The HTMs are thus created for each process topology. This means thatthere are HTMs for a single activity WS-BPEL process, a single activitycontained in a sequence activity, and so forth. FIG. 4( j) illustratesthis process where the node with a pattern most similar to that of theinput data is accessed and/or activated.

In another embodiment, the input data may be based on SCA 1.1. Thus, thepredictive system 611 illustrated in FIGS. 6( a)-6(b) predicts a nextstep or operations for designing an application based on the SCA 1.1. Inthis embodiment, HTMs 601 store deconstructed SCA 1.1 composite aspatterns. The predictive system infers based on how closely the storeddeconstructed composite pattern match the SCA 1.1 composite beingdesigned, or vice versa.

In the predictive design system shown in FIG. 6( a), a user may select aservice 605, which is fed into the predictive system 611. Data of theservice 605 is fed into the predictive system 611, where a node 640 isaccess and activated. The accessed and activated nodes (e.g. node 640 inFIG. 6( a)) are represented with bold lines while non-activated nodes(e.g. nodes 630, 650 in FIG. 6( a)) are represented with dotted lines.

The predictive system 611 then predicts a next task, which may be aservice, a component, a wire, or other appropriate tasks, which arepresented to the user. In other embodiments, as illustrated in FIG. 6(b), the predictive system 611 may even make a longer sequentialprediction by predicting next tasks, which may be a service, a wire, acomponent, a reference, or other appropriate tasks. The predictivesystem 611 makes predictions based on the input data and prior data thatits memory nodes have stored. More information on how the predictivesystem makes predictions based on SCA 1.1 is provided in Section VI.Predictive Application Deployment.

HTMs based on process patterns or process component patternsalternatively provide effective ways of predicting application designs.

B. Based on Process Patterns

Another embodiment of the predictive system may use process patterns forpredicting application designs. In an embodiment, the process patternsare based on WS-BPEL 2.0. FIG. 4( c) illustrates an example of a processdesigned by a user. The process involves a single “receive” activitywhere a message is received on a partner link. Serialized WS-BPEL 2.0process that corresponds to FIG. 4( c) would look substantially similarto the following.

<bpel:process> <bpel:partnerLink name=”myPartnerLink”partnerLinkType=”mywsdl:myPartnerLinkType”/> <bpel:variablename=”myVariable” messageType=”mywsdl:input”> <bpel:sequence><bpel:receive partnerLink=”myPartnerLink” name=”receive” variable=  ”myVariable” operation=”mywsdl:operation”/> </bpel:sequence></bpel:process>

FIG. 4( d) illustrates a process where a WS-BPEL 2.0 process 421 is fedinto the HTM as input. The HTM includes a space for temporal pattern 422and a space for spatial pattern 423. FIGS. 4( e)-4(f) illustrate anembodiment of a user interface 404 interacting with the predictivesystem 411 that uses process models for designing applications. In anembodiment, the space for temporal pattern is substantially the same asthe temporal memory space and the space for spatial pattern issubstantially the same as the spatial memory space. Based on theaforementioned WS-BPEL 2.0 process as input, the predictive system 411can predict the next sequence of steps a user or process designer can ordesires to take for completing the process. In this embodiment, thepredictive system 411 makes these predictions by activating HTM nodesthat most closely match this particular process pattern. Thus, thepredictions are based on HTMs 401 that store the process patterns.

Patterns of previously designed models employing WS-BPEL 2.0 processpatterns are stored in the HTMs 401. Here, patterns can be spatialpatterns or temporal patterns. Spatial patterns 423 are intermediateinstances of the process model as it is getting built. Temporal patterns422 are sequences in which the process was built. Thus, an embodiment ofthe predictive system 411 makes an inference based on how closely thestored process pattern matches the WS-BPEL process being designed. Inanother embodiment, the inference is based on how closely the WS-BPELprocess being designed matches the stored process pattern. While FIGS.4( e)-4(f) do not display a processor or a secondary memory, thesecomponents may be present in the predictive system 411.

In another embodiment, the predictive system may infer for input basedon SCA 1.1. In this case, an SCA 1.1 composite pattern illustrated inFIG. 6(E) may be fed into the HTM of the predictive system. As shown inFIG. 6( c), the predictive system 611 may thus predict next steps oroperations based on the SCA 1.1 composite pattern as input data. Moreinformation on how the predictive system makes predictions based on SCA1.1 is provided in Section VI. Predictive Application Deployment.

C. Based on Process Component Patterns

In another embodiment, the HTMs store WS-BPEL 2.0 process componentpatterns for process model axes. In an embodiment, the axis is aparticular location or instance of the process pattern. Thus, a processcomponent pattern is more specific than the process pattern. In anembodiment, predictions are thus made in a more specific manner. FIG. 4(i) illustrates an embodiment of a user interface 404 interacting withthe predictive system 411 that uses process model component axes fordesigning applications. FIG. 4( g) illustrates an example embodiment ofa process component with axes. FIG. 4( h) illustrates an embodiment ofan HTM that receives a WS-BPEL 2.0 process component 424 as input.Previously designed model component is stored as a pattern for eachmodel axis (for each model component creation step). Spatial patternsare intermediate instances of the process model component as it isgetting built. Temporal patterns are sequences in which the processcomponent was built. Thus, an embodiment of the predictive system 411infers based on how closely the stored process component pattern matchesthe WS-BPEL process component being designed, or vice versa. Memoriesare generated for each process component based on its location or axisin the process model. For example, a sequence activity on the first axishas a set of HTMs for each sequence activity ever designed for thisaxis. The next axis has a set of HTMs for each sequence activity everdesigned for this axis, and so forth. While FIG. 4( i) does not displaya processor or a secondary memory, these components may be present inthe predictive system 411.

In another embodiment, the HTMs store SCA 1.1 composite componentpatterns for model axes. Thus, the input data is based on SCA 1.1composite components. FIG. 6( d) illustrates the predictive system 611making design predictions using SCA 1.1 composite components for eachaxis as input. More information on how the predictive system makespredictions based on SCA 1.1 is provided in Section VI. PredictiveApplication Deployment.

V. HTMs for Predictive Application Design

FIG. 5 illustrates an embodiment of an overall HTM structure 500 for thepredictive system 311 for designing WS-BPEL 2.0-based business processesusing the application design studio. While this embodiment employs anHTM structure focusing on predictions based on topologies, otherembodiments may employ substantially similar HTM structures forpredictions based on process patterns or process component patterns. TheHTM structure 500 has a substantially similar hierarchy to that of amodel defining the WS-BPEL-2.0 based business process, and in thisembodiment, the HTM is employed to predict a configuration of two tasksand a link when the user designs the process as shown in FIGS. 4(a)-4(b). While this embodiment illustrates designing WS-BPEL 2.0-basedbusiness processes, the predictive system 411 may be used for designingbusiness processes that are based on other executable languages. FIG. 7illustrates using SCA 1.1 to make design predictions. More informationon SCA 1.1 is provided in Section VI. Predictive Application Deployment.

The HTM structure 500 includes a hierarchy of levels having memory nodesdepicted as rectangles that receive input data depicted as ovals. Whileeach memory node includes a temporal memory space 503 and a spatialmemory space 504, they are not depicted for every memory node in FIG. 5in order to provide a higher level view of the HTM structure 500. Asillustrated, inputs may be fed into the memory nodes in amulti-hierarchical manner at levels 501, 502(a), (b), 505, and 506.Input data is transmitted by a user via a user interface accessing thepredictive system as illustrated in FIG. 3. The memory nodes identifycombinations of the inputs often received as causes and store the causesin the spatial memory 504. The memory nodes further identify sequentialcombinations of the inputs often received as temporal groups and storethe temporal groups in the temporal memory 503. Based on the causes andthe temporal groups stored in the memory nodes, the memory nodes areoperable to generate predictions with probabilities, where thepredictions with the highest probabilities are passed as beliefs on to anext higher level of memory nodes in the HTM structure 500 as inputs. Inan embodiment, a user may load the HTM structure 500 with initial causesand temporal groups so that it can begin inferring when new input datais fed into its nodes.

In the present embodiment, an input “Op C” 501 enters a memory node atthe lowest level of the HTM structure 500, which generates probabilityinformation on whether one or more of the inputs are associated with oneor more of the causes and with one or more of the temporal groups. Thememory node generates a belief 502(b) based on the probabilityinformation, which is then fed into a memory node at a next higher levelalong with an input “PT C” 502(a).

The memory node at the next higher level then compares the belief 502(b)and the input “PT C” 502(a) with its stored causes and temporal groupsto generate its predictions with probabilities and to form its belief506. This belief-generating behavior is performed by all the memorynodes. The HTM structure 500 outputs a pre-specified number of beliefsas options for next sequences of actions to a user. The pre-specifiednumber of beliefs are generated based on the probability informationgenerated by the memory nodes, wherein the next sequences of actions arebeliefs that are the matched causes and temporal groups with the highestprobabilities at a highest level of the HTM structure 500. In thisembodiment, inputs may be Name, My Role, Partner Role, Op A, Op B, Op C,PT A, PT B, and PT C. These are possible inputs for designing anapplication. But there may be other embodiments of inputs. The memorynodes may be used for different purposes and labeled accordingly, suchas Role, Partner Link Type, Partner Link, Receive Task, Invoke Task,Reply Task, Task Type N, Task, Link, and Process. There may be otherembodiments of labels.

VI. Predictive Application Deployment

An embodiment of the predictive system shown in FIG. 3 may be employedmore specifically for predictive application deployment. The predictivesystem 311 may predict a runtime configuration of an enterpriseapplication as a series of configuration creation/setting steps, whereinthe configuration creation steps can be inferred from the deploymentartifacts. Furthermore, enterprise application runtime configurationsare often, if not always, hierarchical. This is why HTMs or HMMMs areeffective data structures for representing predictions of suchconfigurations.

In an embodiment, the predictive system 311 can predict the runtimedeployment configuration of SCA 1.1 composite, where the predictivesystem 311 makes inferences about next runtime deployment configurationdetail or step based on HTMs 301. The predictive system 311 is capableof predicting deployment configurations based on previously usedconfigurations and/or other relevant historical data. An applicationconfiguration may be mapped into the HTM 301 that has levelssubstantially similar to the hierarchy of the configuration that definesthe application.

In the present embodiment, each memory node of the HTM 301 in thepredictive system 311 has spatial and temporal memory spaces that storecombinations of inputs as causes and sequential combinations of inputsas temporal groups, respectively. Thus, when input data, in anembodiment, a particular service, wire, and/or component are fed into amemory node, the memory node compares the input data with its storedcauses and temporal groups, and the HTM 301 outputs a belief on what thenext deployment configuration task or element should be. In anembodiment, the predictive system may simultaneously predict a number ofconfiguration tasks or elements. The belief at the highest level of thehierarchy of the HTM 301 will be presented to the user as a next stepfor deploying an enterprise application. In an embodiment, a user mayload the HTM 301 with initial causes and temporal groups so that it canbegin inferring when new input data is fed into its nodes. Thepredictive system 311 performs these functions by having the memory 303that stores computer instructions for carrying out the described methodsand the processor 302 that actually executes the computer instructions.The predictive system 311 may be accessed by an end user employing theapplication management system via a cloud system or a local network (asdiscussed above in relation to FIG. 3). This allows accessibility forusers located anywhere around the globe that has access to internet. Thepredictive system 311 thereby predicts by closely modeling the humanbrain function. Since predictions on deployment configurations are madeon similarly deployed applications, users are provided with an optimalway for configuring an application without requiring expert-levelknowledge of a particular enterprise application domain. The system isthus able to act as a trainer for inexperienced users.

In this embodiment, an HTM is employed, but other embodiments may employan HHMM structure or other suitable models. In this embodiment, theinferencing or predicting may be done using three main differentmethods. It may be based on a model topology, composite models orpatterns, or composite component models or patterns for axes.

A. Based on Model Topology

In an embodiment, HTMs store deconstructed SCA 1.1 composite as patternsas illustrated in FIG. 6( i). The predictive system infers based on howclosely the stored deconstructed composite pattern matches the SCA 1.1composite being configured. Thus, in this embodiment, predictions on theconfiguration of an enterprise application are made based on matchingthe topology of the application being deployed. In this case, thepredictive system provides the user with predictions for the service andprocess component runtime configurations, and these predictions maycontinue until the deployment process is complete.

In this embodiment, HTMs are created for each composite topology, andthere are thus HTMs for a single service, component, wire, and so forth.The predictive system therefore predicts on the configuration of theapplications of all permutations and combinations of matching topologyof the application at hand. Each of the topology has an equivalent HTM.The HTM that most closely matches the deconstructed composite patterngets activated and accessed for providing the prediction.

In an embodiment, the runtime environment may be an enterprise server. Amulti-level hierarchy may be defined, a top level consisting of theapplication runtime deployment configuration and a bottom levelconsisting of application runtime deployment configuration components.Here, the application runtime deployment configuration component is partof the application runtime deployment configuration. Table 2 showsexamples of configuration components in case of BPEL component-basedcomposition application.

TABLE 2 Model Component Runtime Deployment Configuration Model SOAP overHTTP Configure SOAP over HTTP Service Binding Service BPEL ComponentConfigure BPEL component properties SOAP over HTTP Configure SOAP overHTTP Reference Binding Reference

The composite application is a collection of configuration components.In an example, consider two application configurations: (1) a servicethat receives a message, a component processes it and sends back areply; (2) a service that receives a message, a component processes it,invokes a reference, and sends back a reply. The structure of theseprocesses are illustrated in FIG. 9. A user configuring a composite thatreceives a message, processes it, and replies back will first configurethe service it is receiving the message on. Thus, the applicationconfiguration or the process configuration is a collection ofconfiguration actions. This application configuration is mapped on to anHTM that has substantially the same levels as the hierarchy of theconfiguration that defines the application.

B. Based on Composite Model

FIG. 6( e) illustrates an example composite designed by a user, whereinthe composite comprises a service, component, and reference. SCA 1.1composite for this example would be substantially similar to thefollowing:

<sca:composite name=”RequestReply”>   <service name=”receiveMsg”>  <component name=”process”>   <reference name=”sendMsg”>  <sca:composite>

Based on the aforementioned SCA 1.1 composite as input data, anembodiment of the predictive system may predict the next sequence ofsteps a composite application deployment engineer may take in order tocomplete the composite application configuration. The predictive systemwill make these predictions by activating the HTMs that closely matchthis particular composite pattern. FIG. 6( f) illustrates an example ofhow an SOAP Over HTTP Service is configured for HTTP. SCA 1.1 Composite621 is fed into an HTM as input. The HTM comprises a space for temporalpattern 622 and a space for spatial pattern 623.

The HTMs store SCA 1.1 composite as patterns. Spatial patterns areintermediate instances of the composite as it is being configured fordeployment, and temporal patterns are a sequence in which the compositewas configured. Inferences are made by the predictive system based onhow closely the stored composite patterns match the SCA composite beingconfigured.

C. Based on Composite Model Components

In an embodiment, HTMs store SCA 1.1 composite component for eachcomposite model axes as patterns. Once again, an axis is a specific orparticular instance or location of a composite model. Thus, a compositemodel component may be more specific than the composite models. In anembodiment, spatial patterns are all the intermediate instances of thecomposite model component deployment configuration as it is beingconfigured, and temporal patterns are sequences in which the compositecomponent was configured for deployment. The predictive system infersbased on how closely the stored composite component pattern matches theSCA composite component being configured. As illustrated in FIG. 6( g),memories are generated for each composite component based on itslocation or axes in the composite model, e.g., service on the firstvertical and horizontal axes has a set of HTMs for each service everdesigned for these axes; for the next vertical axes, there is a next setof HTMs and so forth. FIG. 6( h) illustrates an SCA 1.1 compositecomponent 629 being fed into an HTM as input. The HTM once again has aspace for temporal pattern 622 and a space for spatial pattern 623.

VII. HTM for Predictive Application Deployment

FIGS. 7( a)-7(b) illustrates embodiments of an HTM structure for apredictive system 611 for deploying enterprise applications. While thisembodiment employs an HTM structure focusing on predictions based SCA1.1, other embodiments may be based on other architecture or languages.FIG. 7( a) is more specifically an HTM for predicting service andcomponent configurations, while FIG. 7( b) is more specifically an HTMfor predicting service, component, and reference configurations. Theillustrated HTM structure includes a hierarchy of levels having memorynodes where the memory nodes include temporal memory space and spatialmemory space. Inputs may be fed into the memory nodes in amulti-hierarchical manner. The memory nodes identify combinations of theinputs often received as causes and store the identified combinations ofthe inputs in spatial memory. The memory nodes further identifysequential combinations of the inputs often received as temporal groupsand store the identified sequential combinations of the inputs in thetemporal memory. Based on stored causes and/or temporal groups, thememory nodes generate predictions with probabilities, where thepredictions with the highest probabilities are passed as beliefs to anext higher level of memory nodes in the HTM as inputs. In anembodiment, a user may load the HTM structure 700 with initial causesand temporal groups so that it can begin inferring when new input datais fed into its nodes.

In this embodiment, the HTM is employed to predict a configuration of aservice connected to a component when the user deploys the process.Inputs may be a Port 701, a Name 702, or other relevant data provided bya user. These inputs are multi-hierarchically fed into memory nodeslabeled as HTTP Connector 703, SOAP over HTTP Service 704, SOAP over JMSService 704, BPEL Component 704, JAVA Component 704, Service 705, Wire705, Component 705, or Composite 707. There may be other exemplaryembodiments of components and services. There may also be embodimentsthat predict references in addition to components and services.

VIII. Application in a Managing & Monitoring System

An embodiment of the predictive system may further comprise othercomponents capable of predicting particular aspects of managing andmonitoring enterprise applications. An embodiment may comprise threecomponents, an application deployment component, an applicationmanagement component, and an application monitoring component. Anembodiment of the application deployment component functionssubstantially the same as the aforementioned predictive system fordeploying enterprise applications. Each of these components are equippedwith predictive systems.

In an embodiment, the application deployment component provisions anapplication based on the deployment artifact provided. In mostadministrators, the application artifact is provisioned as is, or a userconfigures the application components that need to be provisioned basedon the preferred configuration parameters. The application deploymentcomponent will comprise an intelligent agent framework based on an HTMthat contains multiple sub-agents that predict on the optimumconfiguration. There will be a hierarchy of intelligent agents makingpredictions on the configuration aspects of the various components. Anexample embodiment of the hierarchy of the intelligent systems thatassist in deployment may look like the following:

Application Deployment Intelligent Agent    Service DeploymentIntelligent Agent       SOAP over HTTP Service Deployment IntelligentAgent    BPEL Component Deployment Intelligent Agent    ReferenceDeployment Intelligent Agent       SOAP over HTTP Reference DeploymentIntelligent Agent

In an embodiment, the application deployment intelligent agent may beresponsible for predicting the application configuration that allows themost optimum way for deploying the application. It may further comprisesub-agents that predict on specific application components. Allpredictions will be merged into sequences of steps ranging from the mostoptimal to the least. In an embodiment, three most optimum sequences ofsteps or options may be presented to the user.

For example, selecting a software port for an HTTP listener may be thetask to be predictably configured. In current administrators, the portis defined in configuration files and there is a chance that thatparticular port has already been deployed to another service. Thus, thepredictive system would select a next available port. The predictivesystem may employ the HTM and predict based on profiles of the user,company, department, and also on the application artifact involved. Thepredictive system will be based on learning the patterns from asuccessfully deployed application and associating it with the profile ofthe user, company, and department. Other variables may also be employed.

To further the example stated above, assume that the application atissue is a bank building software application. Software engineers wouldhave to build it and quality assurance (QA) engineers would have to testit. In most cases, the developers write and test the core functionalityof the component they are building, thereby allowing the QA engineers toperform more in-depth testing. The predictive system would be useful insuch a case. The learning process for such a system begins on a firstsuccessful application deployment. But also, similar data from previoussuccessful application deployments for similar bank software may beloaded on to the predictive system's HTMs. Based on the applicationconfigurations, each memory node stores the predictions and propagates abelief based on a particular application configuration input. Say adeveloper deployed this application, and for example, her profile statesthat the management system can choose any port number for an HTTPlistener. Assuming that 90% of the times the developer lets thepredictive system deploy the application (remaining 10% is where shemanually selects the port number, e.g. between ports 8000-9000), thememory nodes for the HTM that predict on the port number based on thedeveloper profile will have the prediction “choose any available portnumber” at 90% and the predictions of port number between rangescollectively at 10%. The HTM for the entire bank example is shown inFIG. 10.

After the system learns how this particular developer likes to deploy anapplication, on any further deployment having an HTTP listener portselection, the system will be able to provide the user with threechoices: (1) choose any available port; (2) choose between 8000-9000;and (3) choose between 7000-8000. Similarly, for a QA engineer who wantsto test the HTTP listener for all available port ranges, the HTM willpredict based on what it learned from this particular QA engineer. Ifthe QA engineer chooses a port between 1000-9000 with equal probability,on next deployment, the QA engineer will be presented with the randomchoice of the port number ranges.

Port number and selection was provided in this embodiment forillustrative purposes. Other aspects may be predicted in substantiallythe same way.

IX. Example HTM Operations

FIG. 8( a) is a schematic diagram illustrating a user interfaceinteracting with a predictive system 811(a) for designing enterpriseapplications. When a user selects tasks including a service, a link, anda component, data of the tasks get fed into the memory nodes of the HTMof the predictive system 811(a). Memory nodes of the HTM of thepredictive system 811(a) then identify causes and temporal groups of thedata of the tasks. The memory nodes then generate beliefs based on theidentified causes and temporal groups, which allows the predictivesystem 811(a) to make two predictions, one of a next component 802(a)and one of a next reference 803(a). These predictions are presented tothe user as design options, which the user will be able to select from.Once the user selects one of the two options, data of the selectedoption may then be fed into the HTM of the predictive system 811(a). Thememory nodes of the HTM will then identify causes and temporal groups ofthe new data. This process can continue until the user has completed thedesign process. Thus, the predictive system 811(a) assists the user indesigning a business process by predicting the next task or component ofthe business process. While this embodiment illustrates the predictivesystem 811(a) for designing a business process, other embodiments may beused for deploying, managing, or monitoring an enterprise application.

FIG. 8( b) is a schematic diagram illustrating a user interfaceinteracting with a predictive system 811(b) for deploying enterpriseapplications. When a user selects tasks, they get fed into the memorynodes of the HTM of the predictive system 811(b). The predictive system811(b) then outputs two predictions in basic language. In thisembodiment, the configuration options use different sub components suchas different HTTP Connectors, HTTP Ports, or Nodes. But the predictivesystem may generate configuration options for other enterpriseapplications.

While embodiments shown in FIGS. 8( a)-8(b) generate two predictions,other embodiments may generate any number of predictions as desired bythe user. These embodiments refer to deploying enterprise applications,but there may be similar embodiments employing the HTM structure topredict a sequence for modeling an application, managing an application,or monitoring an application. In these embodiments, a profile of a user,a department, a company, and an enterprise application may be fed intothe memory nodes as inputs.

While embodiments shown in FIGS. 4( a), 4(b), 6(a), and 6(b) illustrateinputs that are fed into the HTM in real-time, there may be embodimentswhere stored data comprising causes and temporal groups information maybe fed into the HTM.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above described exemplary embodiments, butshould be defined only in accordance with the claims and theirequivalents.

For example, as referred to herein, a user interface may be a virtualmachine, computer, or host. Also as referred to herein, a network mayrefer to communication channels that facilitate communications betweenuser interfaces and the predictive system. A network may also refer to acommunication medium between processes on the same machine. Also asreferred to herein, a server is a machine deployed to execute a programoperating as a socket listener and may include software instances.Examples of a processor include digital signal processors (DSPs),application-specific integrated circuits (ASICs), field-programmablegate arrays (FPGAs), and any other suitable specific or general purposeprocessors.

Memory may store any suitable information. Memory may comprise anycollection and arrangement of volatile and/or non-volatile componentssuitable for storing data. For example, memory may comprise randomaccess memory (RAM) devices, read-only memory (ROM) devices, magneticstorage devices, optical storage devices, and/or any other suitable datastorage devices. In particular embodiments, memory may represent, inpart, computer-readable storage media on which computer instructionsand/or logic are encoded. Memory may represent any number of memorycomponents within, local to, and/or accessible by a processor.

Various terms used herein have special meanings within the presenttechnical field. Whether a particular term should be construed as such a“term of art,” depends on the context in which that term is used.“Connected to,” “in communication with,” or other similar terms shouldgenerally be construed broadly to include situations both wherecommunications and connections are direct between referenced elements orthrough one or more intermediaries between the referenced elements,including through the internet or some other communicating network.“Network,” “system,” “environment,” and other similar terms generallyrefer to networked computing systems that embody one or more aspects ofthe present disclosure. These and other terms are to be construed inlight of the context in which they are used in the present disclosureand as those terms would be understood by one of ordinary skill in theart would understand those terms in the disclosed context. The abovedefinitions are not exclusive of other meanings that might be impartedto those terms based on the disclosed context.

Words of comparison, measurement, and time such as “at the time,”“equivalent,” “during,” “complete,” and the like should be understood tomean “substantially at the time,” “substantially equivalent,”“substantially during,” “substantially complete,” etc., where“substantially” means that such comparisons, measurements, and timingsare practicable to accomplish the implicitly or expressly stated desiredresult.

Additionally, the section headings herein are provided for consistencywith the suggestions under 37 CFR 1.77 or otherwise to provideorganizational cues. These headings shall not limit or characterize theinvention(s) set out in any claims that may issue from this disclosure.Specifically and by way of example, although the headings refer to a“Technical Field,” such claims should not be limited by the languagechosen under this heading to describe the so-called technical field.Further, a description of a technology in the “Background” is not to beconstrued as an admission that technology is prior art to anyinvention(s) in this disclosure. Neither is the “Brief Summary” to beconsidered as a characterization of the invention(s) set forth in issuedclaims. Furthermore, any reference in this disclosure to “invention” inthe singular should not be used to argue that there is only a singlepoint of novelty in this disclosure. Multiple inventions may be setforth according to the limitations of the multiple claims issuing fromthis disclosure, and such claims accordingly define the invention(s),and their equivalents, that are protected thereby. In all instances, thescope of such claims shall be considered on their own merits in light ofthis disclosure, but should not be constrained by the headings set forthherein.

What is claimed is:
 1. A system for predicting a sequence of operationsfor an enterprise application, the system comprising: a memory thatstores computer instructions for predicting the sequence of operations;hierarchical temporal memories that store data and predict one or morenext operations based on input data transmitted from a user and thestored data; and a processor in communication with the memory and withthe hierarchical temporal memories, the processor operable to executethe computer instructions and to communicate to the user the predictedone or more next operations that are received from the hierarchicaltemporal memories.
 2. The system of claim 1, wherein the hierarchicaltemporal memories comprise a hierarchy of levels having memory nodes,and wherein the memory nodes receive information from lower levels ofmemory nodes as inputs.
 3. The system of claim 2, wherein the memorynodes identify combinations of the inputs often received as causes andstore the identified combinations of the inputs in spatial memory. 4.The system of claim 3, wherein the memory nodes further identifysequential combinations of the inputs often received as temporal groupsand store the identified sequential combinations of the inputs intemporal memory.
 5. The system of claim 4, where a stored database ofcauses and temporal groups can be fed into the hierarchical temporalmemories.
 6. The system of claim 4, wherein the memory nodes generateprobability information as beliefs that one or more of the inputs areassociated with one or more of the causes and with one or more of thetemporal groups.
 7. The system of claim 6, wherein beliefs output frommemory nodes at lower levels enter memory nodes at higher levels asinputs.
 8. The system of claim 7, wherein the memory nodes output apre-specified number of beliefs based on the probability information,wherein the pre-specified number of beliefs comprises causes andtemporal groups with the highest probabilities at a highest level of thetemporal hierarchical memories.
 9. The system of claim 1, wherein thedata stored at the hierarchical temporal memories is dynamic.
 10. Thesystem of claim 1, wherein the data stored at the hierarchical temporalmemories is associated with learned behaviors of the user.
 11. Thesystem of claim 1, wherein the hierarchical temporal memories furtherpredict based on a current state and a user's input.
 12. The system ofclaim 1, further presenting the one or more next operations to a user asa sequence of steps for monitoring an application.
 13. The system ofclaim 1, further presenting the one or more next operations to a user asa sequence of steps for managing an application.
 14. The system of claim13, wherein the inputs are associated with one or more of a profile of auser, a department, a company, and an enterprise application.
 15. Thesystem of claim 8, further presenting the one or more next operations toa user as a sequence of steps for deploying an application.
 16. Thesystem of claim 15, wherein the hierarchical temporal memories predictbased on model topologies.
 17. The system of claim 15, wherein thehierarchical temporal memories predict based on composite models,further wherein the hierarchical temporal memories comprise a space fortemporal patterns and a space for spatial patterns.
 18. The system ofclaim 15, wherein the hierarchical temporal memories predict based oncomposite model components, further wherein the hierarchical temporalmemories comprise a space for temporal patterns and a space for spatialpatterns.
 19. An enterprise application runtime deployment system forpredicting a sequence of operations for deploying an enterpriseapplication, the system comprising: a memory that stores computerinstructions for deploying the sequence of operations; hierarchicaltemporal memories that store data and predict one or more nextoperations based on input data transmitted from a user and the storeddata; and a processor in communication with the memory and with thehierarchical temporal memories, the processor operable to execute thecomputer instructions and to deploy the enterprise application inaccordance with the predicted one or more next operations that arereceived from the hierarchical temporal memories.
 20. The system ofclaim 19, wherein the hierarchical temporal memories predict based onmodel topologies.
 21. The system of claim 19, wherein the hierarchicaltemporal memories predict based on composite models, further wherein thehierarchical temporal memories comprise a space for temporal patternsand a space for spatial patterns.
 22. The system of claim 19, whereinthe hierarchical temporal memories predict based on composite modelcomponents, further wherein the hierarchical temporal memories comprisea space for temporal patterns and a space for spatial patterns.
 23. Amethod for predicting a sequence of operations of an enterpriseapplication, the method comprising: converting behavior associated withenterprise applications to data representative of the behavior; storingthe data representative of the behavior of hierarchical temporalmemories; and predicting one or more next operations based on input datatransmitted from a user and the data stored at the hierarchical temporalmemories.
 24. The method of claim 23, wherein the hierarchical temporalmemories comprise a hierarchy of levels having memory nodes, and whereinthe memory nodes receive information from lower levels of memory nodesas inputs.
 25. The method of claim 24, wherein the memory nodes identifycombinations of the inputs often received as causes and store theidentified combinations of the inputs in spatial memory.
 26. The methodof claim 25, wherein the memory nodes further identify sequentialcombinations of the inputs often received as temporal groups and storethe identified sequential combinations of the inputs in temporal memory.27. The method of claim 26, where a stored database of causes andtemporal groups can be fed into the hierarchical temporal memories. 28.The method of claim 26, further comprising: generating probabilityinformation as beliefs that one or more of the inputs are associatedwith one or more of the causes and with one or more of the temporalgroups.
 29. The method of claim 28, wherein beliefs output from memorynodes at lower levels enter memory nodes at higher levels as inputs. 30.The method of claim 29, further comprising outputting a pre-specifiednumber of beliefs based on the probability information, wherein thepre-specified number of beliefs comprises causes and temporal groupswith the highest probabilities at a highest level of the temporalhierarchical memories.
 31. The method of claim 23, wherein the datastored at the hierarchical temporal memories is dynamic.
 32. The methodof claim 23, wherein the data stored at the hierarchical temporalmemories is associated with learned behaviors of the user.
 33. Themethod of claim 23, wherein the predicting is further based on a currentstate and a user's input.
 34. The method of claim 23, further comprisingpresenting the one or more next operations to a user as a sequence ofsteps for managing an application.
 35. The method of claim 23, furthercomprising presenting the one or more next operations to a user as asequence of steps for monitoring an application.
 36. The method of claim35, wherein data representative of the behavior comprises one or more ofbehavior associated with a profile of a user, a department, a company,and an enterprise application.
 37. The method of claim 30, furthercomprising presenting the one or more next operations to a user as asequence of steps for deploying an application.
 38. The method of claim37, wherein the hierarchical temporal memories predict based on modeltopologies.
 39. The method of claim 37, wherein the hierarchicaltemporal memories predict based on composite models, further wherein thehierarchical temporal memories comprise a space for temporal patternsand a space for spatial patterns.
 40. The method of claim 37, whereinthe hierarchical temporal memories predict based on composite modelcomponents, further wherein the hierarchical temporal memories comprisea space for temporal patterns and a space for spatial patterns.